InfoMagic Internet Tools 1995 April/Internet Tools.iso/dos_win/winsock/maillist/94-02.Z/94-02/text0207.txt

Text File | 1994-02-28 | 5.3 KB | 117 lines

In <[e-mail]> [e-mail] (christopher edward etesse) writes:

>I'm a student consultant at the University of Kentucky
>in Lexington. Currently we are running Mosaic on our Mac's
>here, but would also like to run it on Windows. We are attached
>to a server running Novell v3.11, but are unable to get Moasic
>for windows to run because of a missing winsock. We have tried
>several shareware versions(I believe) but too no avail.
>They did not work with our version of Novell software. Is there
>a winsock out there for Novell v3.11? If so please let me know.
>Also let me know if it costs or if it is something we can try.
>This is not an official U.K inquiry, just something we the
>consultants are experimenting with.
>    Thanks Chris

Try Novell's LAN Workplace for DOS.  Even though it says, "for DOS,"
it actually includes a Windows DLL for using sockets (maybe two).  Two
years ago, when I was working on a Windows TCP/IP project, we used LWP
as the protocol stack and I thought it worked fairly well.  At the
time, however, the WinSock API hadn't yet been established, but LWP
came with a DLL called WLIBSOCK.DLL, which (apparently) supported an
API much the same as that of WINSOCK.  I have to presume that by now,
LWP has a WINSOCK.DLL.

BTW, it's not enough to just have a WINSOCK.DLL... there also has to
be an underlying protocol stack.  WinSock is just a standard interface
to that protocol stack and must be provided by the vendor of the
protocol stack.  Since you're using Novell already, you might look
into theirs.

dmm
--
_____
David M. Miller       |Internet: [e-mail] |Home:  [phone]
Compuserve: 72676,327 |BIX:                 sigmac |Home FAX: "  662-0715
From [e-mail] Sun Feb 20 10:38:39 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA01388; Sun, 20 Feb 1994 15:57:14 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
          id AA01649; Sun, 20 Feb 1994 15:40:09 -0500
Received: from GATEWAY by bigblue with netnews
    for [e-mail] ([e-mail])
To: [e-mail]
Date: Sun, 20 Feb 1994 15:38:39 EST
From: [e-mail] (Patrick Lee)
Message-Id: <[e-mail]>
Organization: E-mail about Stuyvesant H.S. Alumni E-mail Directory
Sender: ses
References: <2k8ah6$[e-mail]>, <[e-mail]>, <2k8btq$[e-mail]>
Subject: Re: I'm ready to spend money - free and shareware WINSOCK not ok

In article <2k8btq$[e-mail]> [e-mail] (Karl Denninger) writes:

>flawlessly.  It is <only> the PC platform that has trouble.  Chameleon is
>known to be ok too, but Chameleon is $400!  For that kind of money it had
><better> work.

Actually, I had a lot of problem getting NetManage to work and finally gave up
(it has not worked for me yet) and moved to Trumpet Winsock.

>Now go into QVT and open some telnet sessions.  When I do that I see long
>pauses in the stream -- it is apparently a problem with <short> packets
>which get held for some indeterminate amount of time.

Do it all the time - QVT Telnet works great and I don't see those long pauses
when connecting to my service provider here. However, if you haven't noticed,
the net as a whole has been very unstable lately. I have been getting long, 30
second, pauses when using Telnet (to sites off my local provider) during
normal U.S. business hours for the past month. Traceroute would tell you that
this is happening on and off at different routers.

>Before you point the finger at QVT I have the same problem with TRMPTEL.

I have no problem with using either Telnet versions - except that I use QVT's
because Trmptel's VT emulation is not complete yet.

>Unfortunately, some of us think that Telnet is an integral part of this
>kind of service and expect that it will work properly.

And it does work!

You have yet to provide any detail on your Trumpet Winsock configuration so
how do you except anyone to help with it? All you have been saying is that it
doesn't work and that your Mac software work. Okay, that means your SLIP
server is set up properly. The fact that Trumpet A17 worked but it did not
starting A18 probably indicates your dialing script is setup incorrectly.
Also, the current version lets you do a manual dial and login. Try that and
see if the SLIP connection is established.

--
Patrick Lee <[e-mail]>
From [e-mail] Sun Feb 20 05:01:26 1994
Received: from netcom8.netcom.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
          id AA01857; Sun, 20 Feb 1994 16:01:08 -0500
Received: from localhost by netcom8.netcom.com (8.6.4/SMI-4.1/Netcom)
    id NAA21035; Sun, 20 Feb 1994 13:01:57 -0800
Date: Sun, 20 Feb 1994 13:01:26 -0800 (PST)
From: Mike Nelson <[e-mail]>
Subject: Winsock, where?
To: [e-mail]
Message-Id: <Pine.3.85.9402201326.A20975-0100000@netcom8>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Where can I find the latest version of Winsock (stable of course <g>),
with SLIP support?

Thanks... Mike.

----------------------------------------------------------------------------
Michael E. Nelson                                         [e-mail]
MailPro for Windows & Win32 Development                  Rockville, Maryland
----------------------------------------------------------------------------